Autogenerated HTML docs for v1.8.1.2-545-g2f19ad 
diff --git a/technical/api-config.html b/technical/api-config.html index 25a27fd..3834067 100644 --- a/technical/api-config.html +++ b/technical/api-config.html 
@@ -736,7 +736,7 @@  <div id="content">   <div id="preamble">   <div class="sectionbody">  -<div class="paragraph"><p>The config API gives callers a way to access git configuration files  +<div class="paragraph"><p>The config API gives callers a way to access Git configuration files   (and files which have the same syntax). See <a href="../git-config.html">git-config(1)</a> for a   discussion of the config file syntax.</p></div>   </div>  @@ -748,7 +748,7 @@  caller-provided callback function. The callback function is responsible   for any actions to be taken on the config option, and is free to ignore   some options. It is not uncommon for the configuration to be parsed  -several times during the run of a git program, with different callbacks  +several times during the run of a Git program, with different callbacks   picking out different variables useful to themselves.</p></div>   <div class="paragraph"><p>A config callback function takes three parameters:</p></div>   <div class="ulist"><ul>  @@ -782,7 +782,7 @@  <h2 id="_basic_config_querying">Basic Config Querying</h2>   <div class="sectionbody">   <div class="paragraph"><p>Most programs will simply want to look up variables in all config files  -that git knows about, using the normal precedence rules. To do this,  +that Git knows about, using the normal precedence rules. To do this,   call <code>git_config</code> with a callback function and void data pointer.</p></div>   <div class="paragraph"><p><code>git_config</code> will read all config sources in order of increasing   priority. Thus a callback should typically overwrite previously-seen  @@ -793,7 +793,7 @@  value is left at the end).</p></div>   <div class="paragraph"><p>The <code>git_config_with_options</code> function lets the caller examine config   while adjusting some of the default behavior of <code>git_config</code>. It should  -almost never be used by "regular" git code that is looking up  +almost never be used by "regular" Git code that is looking up   configuration variables. It is intended for advanced callers like   <code>git-config</code>, which are intentionally tweaking the normal config-lookup   process. It takes two extra parameters:</p></div>  @@ -821,7 +821,7 @@  <div class="paragraph"><p>There is a special version of <code>git_config</code> called <code>git_config_early</code>.   This version takes an additional parameter to specify the repository   config, instead of having it looked up via <code>git_path</code>. This is useful  -early in a git program before the repository has been found. Unless  +early in a Git program before the repository has been found. Unless   you&#8217;re working with early setup code, you probably don&#8217;t want to use   this.</p></div>   </div>  @@ -939,7 +939,7 @@  <div id="footnotes"><hr /></div>   <div id="footer">   <div id="footer-text">  -Last updated 2012-06-08 11:37:18 PDT  +Last updated 2013-02-05 21:07:26 PST   </div>   </div>   </body>